Update @marko/compiler to 5.41.7 and marko to 5.39.27 - #577
Conversation
🦋 Changeset detectedLatest commit: fa800fe The changes in this PR will be included in the next version bump. This PR includes changesets to release 5 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 17 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (6)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
f05dad2 to
b9b2d7b
Compare
5.41.7 carries two fixes this repo needs. 5.41.5 shipped a dangling
`require("@babel/preset-typescript/package.json")`, which broke the
ts-plugin and marko-vscode bundles; 5.41.5 and 5.41.6 then published
`internal/babel` as `"type": "commonjs"` over an ESM `index.ts`, which
failed `tsc -b` with TS1295 under `verbatimModuleSyntax`.
marko 5.39.27 requires `@marko/compiler ^5.41.4`, so the compiler is
bumped in step to keep a single instance installed — a second copy makes
the translator read compilation state from the wrong module and fail with
`Unable to access Marko File outside of a compilation`.
The changeset covers ts-plugin and marko-vscode as well, since those are
the two packages that inline the compiler and so need releases to ship
fixed artifacts.
b9b2d7b to
fa800fe
Compare
DylanPiercey
changed the title
1 participant
Picks up
@marko/compiler@5.41.7, which carries two fixes this repo needs:require("@babel/preset-typescript/package.json"), breaking the@marko/ts-pluginandmarko-vscodeesbuild bundles withCould not resolve "@babel/preset-typescript/package.json"(Stub the preset-typescript version read in dist/babel.js marko#3583).internal/babelas"type": "commonjs"over an ESMindex.ts, failingtsc -bwithTS1295underverbatimModuleSyntax(Publish internal/babel as ESM, matching what it ships marko#3586).markomoves to 5.39.27, which requires@marko/compiler ^5.41.4; the compiler range is bumped in step so only one copy is installed. Two copies make the translator read compilation state from the wrong module instance and fail withUnable to access Marko File outside of a compilation.The changeset covers
@marko/ts-pluginandmarko-vscodetoo, since those are the packages that inline the compiler and need releases to ship fixed artifacts.Verified:
pnpm why @marko/compilerreports a single version resolving to 5.41.7, 0 TypeScript errors, all five packages build, 189 tests passing.